⚠️ No Changeset found

Latest commit: bc6fd8c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Initial thoughts:

@Mist3rBru Great Work 🙏🏼 ,

I actually kinda of like this.. This could be a great addition. I'm just not for sure on the namespace builder. It almost sounds to me like a workflow. What are your thoughts?

Additional thoughts

I also think, within the next couple of releases -- I want to focus on knocking out a few bugs reported, then exposing each individual core prompt interface types to make it agnostic vs duplicating types that are already exist in core. This way someone can easily build on top of core as an agnostic layer like what we do for @clack/prompts. Then we can add another layer for themes etc.

Thanks,
CP 🚀

I agree, sounds more like an workflow, it could also change the add method to step.
Example:

await p.workflow()
  .step('name', () => p.text())
  .run()

@Mist3rBru I like that.

My only questions here

1. Should we deprecate groups in favor on this ?
2. Since this is the same functionality as group a end user might ask Which one do I use ?

We can release it, and open a pinned issue like v1.0.0 Roadmap, so people can give their thoughts, and we decide based on it.

I think it is a better API, since it does not deal with inference errors, and is more extensible.

@Mist3rBru I made some improvements to examples please check this out: de9f5b6

@cpreston321 commit included.

This helps a lot to run the examples!

Open in Stackblitz • @example/basic • @example/changesets

npm i https://pkg.pr.new/bombshell-dev/clack/@clack/core@139

npm i https://pkg.pr.new/bombshell-dev/clack/@clack/prompts@139

commit: bc6fd8c